bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Sun, 3 Feb 2019 16:27:51 +0000 (16:27 +0000)
committerSylvestre Ledru <sylvestre@debian.org>
Sun, 3 Feb 2019 16:27:51 +0000 (16:27 +0000)
commitc154c4da2819d2425dff33609b33fa716c6930e9
tree78993ddc79617319951cbc3f851fa6f575a1d384
parent64333626a4948cf131e067637d0b194f2a12a417
bootstrap-fix-include-next

When doing a bootstrap, we use a newly built clang.
When this one is used, if already installed on the system,
we have clang header in two places:
llvm-toolchain-7-7/build-llvm/lib/clang/7.0.0/include/inttypes.h
and
/usr/include/clang/7.0.0/include/inttypes.h

Because clang expects only one of his headers to be available, it uses
include_next to get the glibc (libc6-dev package) header.

However, in the previous example, because we have inttypes.h twice in the
include search path, clang's header will call itself without any effect.
Therefore, it will do include_next until the define from the libc is existing (ex: _INTTYPES_H)

Gbp-Pq: Name bootstrap-fix-include-next.diff
clang/lib/Headers/inttypes.h
clang/lib/Headers/limits.h